Skip to content

chore(deps): update dependency eslint to v10#9972

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-eslint-monorepo
Open

chore(deps): update dependency eslint to v10#9972
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-eslint-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 9, 2026

This PR contains the following updates:

Package Change Age Confidence
eslint (source) ~9.39.0~10.0.0 age confidence

Release Notes

eslint/eslint (eslint)

v10.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Feb 9, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: ui/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-plugin-import@2.32.0
npm error Found: eslint@10.0.0
npm error node_modules/eslint
npm error   dev eslint@"~10.0.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.9.1
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.1.2" from eslint-plugin-es-x@7.8.0
npm error     node_modules/eslint-plugin-es-x
npm error       eslint-plugin-es-x@"^7.8.0" from eslint-plugin-n@17.23.2
npm error       node_modules/eslint-plugin-n
npm error         dev eslint-plugin-n@"~17.23.0" from the root project
npm error     @eslint-community/eslint-utils@"^4.5.0" from eslint-plugin-n@17.23.2
npm error     node_modules/eslint-plugin-n
npm error       dev eslint-plugin-n@"~17.23.0" from the root project
npm error     3 more (eslint-plugin-promise, eslint, eslint)
npm error   5 more (eslint-compat-utils, eslint-plugin-es-x, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9" from eslint-plugin-import@2.32.0
npm error node_modules/eslint-plugin-import
npm error   dev eslint-plugin-import@"~2.32.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@9.39.2
npm error node_modules/eslint
npm error   peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9" from eslint-plugin-import@2.32.0
npm error   node_modules/eslint-plugin-import
npm error     dev eslint-plugin-import@"~2.32.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-13T10_27_20_195Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-13T10_27_20_195Z-debug-0.log

@renovate renovate bot requested review from a team as code owners February 9, 2026 11:09
@renovate renovate bot force-pushed the renovate/major-eslint-monorepo branch 4 times, most recently from c010f6f to 29f726a Compare February 10, 2026 06:28
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

"browserify": "~17.0.0",
"cssnano": "~7.1.0",
"eslint": "~9.39.0",
"eslint": "~10.0.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ESLint v10 incompatible with legacy .eslintrc config

High Severity

ESLint v10 removed support for the legacy eslintrc configuration format (.eslintrc files) and requires flat config (eslint.config.js/eslint.config.mjs). The project still uses a .eslintrc file with "extends": "standard" and has no flat config file. Bumping eslint to ~10.0.0 without migrating the configuration means any direct invocation of eslint will fail to pick up the project's linting rules. The gulp-eslint v6 build task bundles its own ESLint v6 so it may still work, but the top-level eslint devDependency becomes non-functional.

Fix in Cursor Fix in Web

@renovate renovate bot force-pushed the renovate/major-eslint-monorepo branch 12 times, most recently from c3b00ed to a9faeab Compare February 13, 2026 10:22
@renovate renovate bot force-pushed the renovate/major-eslint-monorepo branch from a9faeab to 24f61f3 Compare February 13, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants